home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EnigmA Amiga Run 1995 October
/
EnigmA AMIGA RUN 01 (1995)(G.R. Edizioni)(IT)[!][issue 1995-10][Aminet 7].iso
/
Aminet
/
comm
/
cnet
/
cnettoolkit2a.lha
/
FPButton.README!
< prev
next >
Wrap
Text File
|
1994-12-16
|
4KB
|
109 lines
============================================================================
FPButton (Flux Point VDE Buttons) README! by PMK
============================================================================
The following text was originally written by Pete. I cleaned it up a bit,
but other than that it appears exactly as Pete sent it to me. There is also
a file titled "FPButton" included in this archive that shows you an example
on using Pete's technique for creating a VDE-type config editor. Please feel
free to chop it up for use in your own files and/or creations or else use the
tehniques Pete discusses below to embellish your own programs, but we would
ask that you PLEASE SHARE WHATEVER YOU COME UP WITH! :-) Happy Holidays!
How to create your own buttons using FPButton.
------------------------------------------------
Each button is defined by a series of variables, containing the type,
position, etc. The first variable set is the position (x & y coords.),
defined like this:
XC.<#>=<X coord.>
YC.<#>=<Y coord.>
The <#> is the number of this button. This number is used for the next
set of variables, which are the movement variables:
ML.<#>=<M#> (Move LEFT variable)
MR.<#>=<M#> (Move RIGHT variable)
MU.<#>=<M#> (Move UP variable)
MD.<#>=<M#> (Move DOWN variable)
Again, <#> is the number of this button. <M#> is the button the cursor
should move to, when the appropriate direction is selected. If the cursor
isn't allowed to move in a direction, then set the <M#> to 0.
The next variable is the button itself, and is defined like this:
but.<#>="\c7\z4Text for Button\z0\c7 "
The button variable should always contain 12 MCI chars, (like 4 sets of
color changes etc.), as this number is used to get the correct position
later on in the program. (Can be changed if you also change the '12' in the
main routines)
The next variable is the Type of button you want:
bty.<#>=<type>
Four types of buttons exists:
"0" is an ACTION BUTTON.
When an ACTION BUTTON is pressed, the program calls a subroutine,
called 'BUTTON<#>' where <#> is the number of the button. It is up
to you to define this routine in the program! REMEMBER to end it
with a RETURN command. Here's an example of an action button:
BUTTON51:;exi=1;return
"1" is a TOGGLE BUTTON.
A TOGGLE BUTTON toggles between Yes and No (1 and 0).
"2" is a STRING BUTTON.
A STRING BUTTON has an additional button variable to control the
length and MCI input options. This variable looks like this:
le.<#>="<MCI opt> <length>"
Where <#> is the button number.
<MCI opt> is any legal MCI input option PLUS THE NUMBER 4!!!
So if you want the input to be numeric only (MCI opt. 64),
then this value would be 64+4=68!!
<length> is the maximum length of the input requester.
"3" is a CYCLE BUTTON.
A CYCLE BUTTON is very similar to the TOGGLE BUTTON, but requires
two additional button variables, defined like this:
mc.<#>=<cycles>
cnm.<#>="<var name>"
Where <#> is the button number.
<cycles> is the number of cycle options.
<var name> is the NAME OF THE VARIABLE, that holds the cycle
options.
These variables should be defined in the start of the program,
like this:
cyc.0='Arexx ';cyc.1='CNet C ';cyc.2='DOS ';cyc.3='Paragon'
Then the two button variables would look like this:
mc.<#>=4 (4 different options (0-3))
cnm.<#>='cyc' (the name of the button definitions is 'cyc')
============================================================================
$VER: FPButton 1.01 (27.03.94) by PMK
============================================================================